- 11 minutes to read

IBM MQ Monitoring Configuration

Unlock secure, proactive monitoring for all your IBM MQ resources with Nodinite. On this page, you will learn how to:

✅ Configure the IBM MQ Monitoring Agent for queues, topics, channels, and listeners
✅ Enable SSL for secure communication and compliance
✅ Set global and specific thresholds for proactive alerting
✅ Use remote configuration and actions for rapid management
✅ Group and filter resources for streamlined operations

Note
Before you can monitor and remotely configure IBM MQ, install the Nodinite IBM MQ Monitoring Agent and create a Monitoring Agent Configuration. Start here if you are a first-time user.

Remote Configuration

As a Nodinite Administrator, click the 'Configuration' button to open a modal and configure the agent:

The Configuration button appears in the Monitoring Agent Configuration administration page.

Adjust configurations on the Resource by using the Action button if the Monitor View has the Remote Actions feature enabled.

The system groups Resources per host by Application and then by Category using the value from the Name text field. Read more about Applications here:

Applications

The system groups all resources for one Queue Manager by the user-friendly Display Name you set in the next step.

Configuring the connection

Add broker
Remove broker
Enable broker
Disable broker
Apply exclusion filters
Manage Queue thresholds
- Global - Use if you do not override with a specific setting
- Specific - Overrides global configuration on a named queue
Authentication

Click the Save button to persist your changes. Nodinite will reflect changes after the user-defined synchronization interval.

Add IBM MQ broker

From the Monitoring tab, manage any number of IBM MQ brokers, each with its own set of properties.

Update Source Interval

Set the Update Source Interval (seconds) to control how frequently the agent polls all IBM MQ Queue Managers for status updates. The default value is 30 seconds.

Update Source Interval (seconds) - Global polling interval for all IBM MQ Queue Managers (default: 30)

Lower values provide more frequent updates but increase system load. Higher values reduce load but delay status visibility.

Adding Queue Managers

To monitor and control one or more IBM MQ brokers, provide basic connection details.

Example: Add IBM MQ Queue Managers to monitor.

Click the Add button to add an IBM MQ Queue Manager to monitor. Repeat as needed.

Example: One Accordion per IBM MQ Queue Manager entry.

Expand the Accordion to configure the connection.

Example: Basic tab for IBM MQ Queue Manager configuration.

Enable IBM MQ monitoring - When checked, monitor the specified IBM MQ queue manager
Display Name - Display name for the configuration of the specified Queue Manager (This also becomes the Application name)
Description - Optional description for this configuration
Server - Address of the Queue Manager (hostname or IP address)
Manager - Name of the Queue Manager
Port - Set the Port number to use, the default is 1414
Channel - Channel name for IBM MQ Service communication

SSL

To use SSL, check the Use SSL checkbox.

Example: SSL Configuration for IBM MQ Queue Manager.

Use SSL - When checked, the active channel requires a TLS/SSL connection ^{New 5.4.1.6}
SSL CipherSpec - Select the CipherSpec to use in the SSL conversation
SSL Key Repository - Specify the Windows Certificate Store to use: '*SYSTEM' for system-wide store or '*USER' for current user store
SSL Peer Name Property - Accept only certificates with Distinguished Names matching these values
SSL Certificate Label - The certificate's 'Friendly Name' from the Windows Certificate Store (e.g., 'ibmwebspheremq')

SSL Certificate Requirements

IBM MQ SSL authentication requires properly configured certificates on both Queue Manager (server) and Nodinite agent (client) sides.

Certificate Storage:

The IBM MQ Monitoring Agent uses the Windows Certificate Store for SSL certificates. Specify either:

*SYSTEM - System-wide certificate store (all users)
*USER - Current user certificate store

Certificate Purpose Requirements:

Side	Required EKU	Purpose
Queue Manager	Server Authentication (1.3.6.1.5.5.7.3.1)	Authenticates Queue Manager to agent
Nodinite Agent	Client Authentication (1.3.6.1.5.5.7.3.2)	Authenticates agent to Queue Manager (mutual TLS)

Tip
Certificate Setup Guidance: See FAQ: IBM MQ SSL Certificate Configuration for detailed instructions on certificate conversion, keystore configuration, and troubleshooting SSL handshake errors.

Note
The SSL Certificate Label must match the certificate's "Friendly Name" property in the Windows Certificate Store. Use the Certificates MMC snap-in to verify the correct friendly name.

Remove IBM MQ broker

Click the Remove button to delete the configuration for monitoring the IBM MQ broker and its queue Resources.

The 'Remove' button deletes the IBM MQ broker configuration from monitoring.

If you want to keep your configuration but stop monitoring, disable the Monitoring instead of removing the broker.

Enable IBM MQ broker

The system marks a disabled Monitoring Configuration with a ban sign. You can only enable disabled brokers.

A disabled IBM MQ broker displays a ban sign.

Check the box to re-enable monitoring of IBM MQ broker Resources.

The system enables IBM MQ broker Monitoring when you check the box.

Disable IBM MQ broker

You can stop monitoring the IBM MQ broker without removing the configuration by disabling the selected configuration. An enabled Monitoring Configuration does not display the ban sign. You can only disable enabled IBM MQ brokers.

Enabled IBM MQ brokers do not display a ban sign.

Uncheck the box to disable monitoring of IBM MQ broker Resources.

Filters

Use the Filters tab to control which IBM MQ resources to monitor and exclude from discovery.

Example: Filters tab for IBM MQ Queue Manager configuration.

Resource Type Selection

Control which types of IBM MQ resources the agent monitors:

Filter System Queues, Topics, Listeners and Channels - When checked, exclude items starting with 'SYSTEM.' (usually for internal use only)
Include Local Queues - When checked, monitor local queues (queues that physically exist on this queue manager)
Include Remote Queues - When checked, monitor remote queue definitions (pointers to queues on other queue managers)
Include Model Queues - When checked, monitor model queues (templates used to create dynamic queues)
Include Alias Queues - When checked, monitor alias queues (alternative names that point to queues or topics)
Include Cluster Queues (requires Local Queues) - When checked, monitor cluster queues (local queues that participate in a queue manager cluster). NOTE: Cluster queues ARE local queues with cluster membership, so 'Include Local Queues' must also be enabled for this to work.
Include Channels - When checked, monitor IBM MQ channels (communication links between queue managers or clients)
Include Listeners - When checked, monitor IBM MQ listeners (processes that listen for incoming connections)
Include Topics - When checked, monitor IBM MQ topics (publish/subscribe topic definitions)

Performance Options

Enable message age monitoring - When checked, track the oldest message in each queue. WARNING: This can significantly impact performance with large queue counts (50+ queues). Message age queries may double total query time.

Custom Filters

Use the Filters section to define RegEx patterns that filter resources. By default, patterns EXCLUDE matching items. Prefix with '!' to INCLUDE only matching items (e.g., '!^PROD' includes only items starting with PROD). Case insensitive.

Click the Add button to add a new filter pattern. Each filter entry has:

Enabled - When checked, this filter entry is active
Filter expression - RegEx pattern for filtering resources

Example #1: Exclude resources that do not contain '.BO'

^((?!\.BO).)*$

Example 1: Removes all entries that do not match the '.BO' name pattern using negative lookahead.

Example #2: Exclude resources starting with underscore

^[_].*

Example 2: Removes all entries starting with the underscore character '_'.

Example #3: Include only PROD resources

!^PROD

Example 3: Uses the '!' prefix to include only items starting with 'PROD', excluding all others.

Example #4: Exclude SYSTEM resources

^SYSTEM\.

Example 4: Excludes items starting with 'SYSTEM.' (typically IBM MQ internal resources).

Tip
Learn more about Regular Expression Lookaround Assertions in Microsoft's .NET documentation.

Manage Queue thresholds

Set queue settings as either global or override them with specific settings.

The system uses global settings to evaluate queues unless you set specific settings.

Example: Queue thresholds tab for IBM MQ Queue Manager configuration.

Global Threshold Settings

Configure time-based and count-based thresholds that apply to all queues unless overridden by specific settings.

Time-based Thresholds

The system always evaluates time-based thresholds based on the age of the oldest message in the queue.

Warning Time Span - The longest allowed timespan for first message on queue (days:hours:minutes:seconds e.g 7.12:30:59)
Error Time Span - The longest allowed timespan for first message on queue (days:hours:minutes:seconds e.g 7.12:30:59)

Queue Depth Evaluation Type

Select how to evaluate queue depth monitoring:

None - Disable queue depth monitoring
Fixed - Monitor based on absolute message count
Percent - Monitor based on percentage of queue quota
Which comes first (both) - Monitor using both Fixed and Percent, triggering on whichever threshold is reached first

Count-based Thresholds (Fixed)

When using Fixed or Which comes first (both) evaluation:

Warning Count - Set the threshold for maximum number of messages (disable by setting < 0)
Error Count - Set the threshold for maximum number of messages (disable by setting < 0)

Percentage-based Thresholds

When using Percent or Which comes first (both) evaluation:

Warning Limit % - Set the threshold quota value in percentage (0-100)
Error Limit % - Set the threshold quota value in percentage (0-100)

Specific Queue Settings

Options for overriding global/default values on specific queues.

Set specific thresholds for named queues to override global configuration.

Add one or more named queues to provide specific settings.

Identify each specific queue by its queue name. You can also add a user-friendly description.

All other properties match those described in the global configuration.

Tip
Perform specific configurations more easily using the Edit threshold menu item on the Actions button in the list of queues (Resources) with Monitor Views and Remote Actions Option enabled.

Advanced

Configure advanced performance settings for the IBM MQ Monitoring Agent.

Example: Advanced tab for IBM MQ Queue Manager configuration.

Poll Timeout

Poll Timeout - The number of seconds to wait before timing out PCF queries to this Queue Manager. Increase this value (e.g., 300-600) for environments with 10,000+ queues. Default: 110 seconds

Authentication

Control authentication for the IBM MQ Queue Manager connection.

Example: Authentication tab for IBM MQ Queue Manager configuration.

Use authentication - When checked, authenticate connection using the provided credentials
User name - The name of the 'User' account with proper access rights
Password - The password for the user

Note
Leave Use authentication unchecked if the IBM MQ Queue Manager is configured for anonymous access or uses operating system credentials.

Save

Click 'Save' or 'Save and close' to persist your changes. The system evaluates new settings/thresholds on the next synchronization.

The Save options example.

Note
The delay in presenting the new evaluated state depends on the synchronization interval set for the monitoring agent. Click the Sync Now button to force an immediate synchronization.

Save and close saves and closes the dialogue.
Cancel closes the dialogue without saving any changes.

Note
Changes to configuration appear in Web Client after the 'Polling Interval' delay. Click the Sync Now button to force Nodinite to synchronize with the agent immediately.

Settings tab

Within the Settings tab, provide details that determine how the IBM MQ Monitoring Agent operates.

Environment

Set the name of the target environment (for example, TEST, QA, PROD). This feature is standard for all Monitoring Agents.

Debug

Enable or disable the Debug flag for additional file logging as needed. The system leaves this unchecked by default. This feature is standard for all Monitoring Agents.

Culture Information

The Culture Information setting controls how the agent presents time-based data in the Web Client/Web API.

AI Diagnostics

^{New 7.0.4}

Enable AI Diagnostics to automatically analyze errors and warnings from monitored IBM MQ queue managers and queues. When issues occur, AI Diagnostics provides intelligent root cause analysis and actionable recommendations to accelerate troubleshooting.

Tip
Learn more about configuring and using AI-powered diagnostics in the AI Diagnostics documentation.

Add IBM MQ Monitoring Agent Configuration

After you install the IBM MQ Monitoring Agent, provide Nodinite with connection details so the Monitoring Service can detect the new agent.

No one can monitor or configure the IBM MQ Monitoring Agent until you complete the steps below.

Configuration Steps

Add and configure a new Monitoring Agent Configuration
- Find connection information in the README.txt file in the installation folder
Use the Remote Configuration feature to configure the agent. See the beginning of this user guide for details.
Create one or more self-service enabled Monitor Views that include the selected Resources provided by the IBM MQ Monitoring Agent according to your business needs.
- Add or manage Monitor View
Fine-tune specific settings directly on Resources using Remote Actions

Frequently asked questions

Use the troubleshooting guide to find the FAQ and answers to known problems.

Next Step

Add or manage a Monitoring Agent Configuration
Add or manage Monitor View

Install IBM MQ Monitoring Agent
Update
Monitoring Agents
Applications

Explore Nodinite for 30 days – completely free

See how Nodinite resolves your technical issues, in a

LIVE Demo!